Background

The CI build tasks that build the Windows app are flaky through no fault of our own. Currently, the windows and windows-template jobs are hard dependencies of the release job, meaning if they fail, the entire pipeline is blocked.

Goal

Make the Windows build jobs optional (non-blocking) but still surface as a visible warning when they fail.

Changes required in .github/workflows/build.yml

1. Add continue-on-error: true to the windows job

  windows:
    name: "Windows"
    permissions: {}
    runs-on: windows-2025
    continue-on-error: true          # ← ADD THIS
    if: ${{ github.event_name != 'schedule' }}

2. Add continue-on-error: true to the windows-template job

  windows-template:
    name: "Windows [template]"
    permissions: {}
    runs-on: windows-2025
    continue-on-error: true          # ← ADD THIS
    if: ${{ github.event_name != 'schedule' }}

3. Add a new windows-result aggregator job

Insert this new job after windows-template and before release. It runs after both Windows jobs complete (regardless of outcome) and emits a ::warning:: annotation if either failed:

  windows-result:
    name: "Windows [result]"
    permissions: {}
    runs-on: ubuntu-24.04
    if: ${{ github.event_name != 'schedule' }}
    needs:
      - windows
      - windows-template
    steps:
      - name: Warn if Windows builds failed
        if: ${{ contains(needs.*.result, 'failure') }}
        run: |
          echo "::warning::One or more Windows build jobs failed. This is non-blocking but should be investigated."
          echo "windows result: ${{ needs.windows.result }}"
          echo "windows-template result: ${{ needs.windows-template.result }}"

4. Update the release job's needs: list

Replace the direct dependencies on windows and windows-template with the new windows-result aggregator job:

  release:
    needs:
      - review
      - ios
      - ios-template
      - android
      - android-template
      - macos
      - macos-template
      - windows-result          # ← replaces `windows` and `windows-template`

Expected outcome

• Both Windows jobs can fail without blocking the CI pipeline (shown as ⚠️ in the GitHub UI instead of ❌)
• The ::warning:: annotation in windows-result surfaces the failure prominently in the PR annotations panel
• The release job waits for windows-result (which always succeeds on its own) and is no longer blocked by Windows flakiness
• All non-Windows jobs are completely unaffected